-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WithGivens for monoidal and (co)cartesian derivations #1494
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you please
- rebase;
- add a first commit to bump the version and the dependency of the three packages
CAP
,FreydCategoriesForCAP
andLinearAlgebraForCAP
; - add a last commit bumping the version of
MonoidalCategories
andCartesianCategories
.
25bd48e
to
c6ff115
Compare
In the first commit please also bump the dependency on the released |
c6ff115
to
e8f0492
Compare
##TODO: Use BraidingWithGiven | ||
return InverseForMorphisms( cat, Braiding( cat, object_1, object_2 ) ); | ||
|
||
return BraidingWithGivenTensorProducts( cat, object_2_tensored_object_1, object_2, object_1, object_1_tensored_object_2 ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This only holds in symmetric categories, and already exists in SymmetricMonoidalCategoriesDerivedMethods.gi
.
@@ -879,7 +879,7 @@ AddDerivationToCAP( CartesianPostComposeMorphismWithGivenObjects, | |||
|
|||
braiding := CartesianBraiding( cat, ExponentialOnObjects( cat, b, c ), ExponentialOnObjects( cat, a, b ) ); | |||
|
|||
return PreCompose( cat, braiding, CartesianPreComposeMorphism( cat, a, b, c ) ); | |||
return PreComposeList( cat, source, [ braiding, CartesianPreComposeMorphism( cat, a, b, c ) ], range ); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think this is the desired solution. The source of PreCompose
is the source of the first morphism, i.e. the source of braiding
. So the desired solution is that braiding
has the expected source in the first place.
Thinking more about this, I think we should never use PreComposeList
for literal lists. The information about source and range is already available in this case, so adding source and range explicitly does not add anything if everything else is correct. And if things are wrong, adding source and range only hides actual errors. For example, if braiding
would have the wrong source here, using PreComposeList would just hide the wrong source from CompilerForCAP.
@TKuh: Could you please make a separate PR out of the first commit? This should fix gap-system/PackageDistro#846. |
46d99cc
to
da8624c
Compare
da8624c
to
9698af4
Compare
Depends on #1492
Part of #1239